Note
This does not works in browser for quests which require you to play a game! Use the desktop app to complete those.
How to use this script:
Console tab
[Environment variables][7] are a set of dynamic named values that can affect the way running processes will behave on a computer. The variables can be used both in scripts and on the command line. Environment variables makes it easy when certain standard directories and parameters need to be referenced but where the actual locations or names can vary from computer to computer.
This tutorial will show you a complete list of environment variables that can be used to reference standard directories and parameters in Windows 10.
Tip
See the blog post: https://mdinata.my.id/blog/posts/docker-on-postmarketos/
With postmarketOS and modified kernel (see https://blog.hypriot.com/post/verify-kernel-container-compatibility/), it's possible to natively run Docker on phone. Since postmarketOS runs Alpine Linux natively, there's no need to run VMs, chroot, or whatever it is. Just native. Ain't that cool?
| #include <stdio.h> | |
| #include <stdlib.h> | |
| #include <time.h> | |
| int xs[] = {7,62,2,46,73,43,26,82,5,95,57,56,44,21,40,79,13,6,9,8,72,59,65,81,60,78,13,85,87,58,48,25,32,47,67,4,31,19,33,1,92,14,53,89,84,54,29,10,17,3,77,70,45,97,34,23,86,55,15,64,68,83,76,41,18,39,94,22,74,11,69,49,12,35,20,90,100,98,36,63,91,38,66,93,50,96,61,71,75,37,52,88,30,28,99,27,42,51,80,24,16}; | |
| int main() | |
| { | |
| int x = 0; | |
| for (int i = 1; i <= 100; ++i) { |
This guide walks through getting the Roboflow Inference Server running on a Jetson Orin Nano, and verifying it with a small Python test script.
It assumes you have already done the basic Jetson setup from this gist:
The overall process closely follows the official Roboflow docs:
| ### | |
| # Toggle an external light from the X1C screen | |
| ### | |
| alias: Bambu Lab - Auto External Light | |
| description: "" | |
| trigger: | |
| - platform: state | |
| entity_id: | |
| - light.x1c_chamber_light | |
| from: null |
This is a note for myself describing various Visual Basic macros construction strategies that could be used for remote code execution via malicious Document vector. Nothing new or fancy here, just a list of techniques, tools and scripts collected in one place for a quick glimpse of an eye before setting a payload.
All of the below examples had been generated for using as a remote address: 192.168.56.101.
List:
| "use client"; | |
| /* eslint-disable @next/next/no-img-element */ | |
| import Link from "next/link"; | |
| import { useState, useEffect } from 'react'; | |
| import { | |
| AppBskyFeedDefs, | |
| AppBskyFeedPost, | |
| type AppBskyFeedGetPostThread, | |
| } from "@atproto/api"; |
